Data bus bandwidth scheduling in an fbdimm memory system operating in variable latency mode

ABSTRACT

A method and system for scheduling the servicing of data requests, using the variable latency mode, in an FBDIMM memory sub-system. A scheduling algorithm pre-computes return time data for data connected to all DRAM buffer chips and stores the return time data in a table. The return time data is expressed as a set of data return time binary vectors with one bit equal to “1” in each vector. For each received data request, the memory controller retrieves the appropriate return time vector. Additionally, the scheduling algorithm utilizes an updated history vector representing a compilation of data return time vectors of all executing requests to determine whether the received request presents a conflict to the executing requests. By computing and utilizing a score for each request, the scheduling algorithm re-orders and schedules the execution of selected requests to preserve as much data bus bandwidth as possible, while avoiding conflict.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention generally relates to computer memory systems and in particular to accessing data in computer memory systems. Still more particularly, the present invention relates to scheduling access to memory data within computer memory systems.

2. Description of the Related Art

In a data processing system, requests for data stored within memory (memory data) are received by a memory controller, which controls access to the memory data. In a Fully Buffered Dual Inline Memory Module (FBDIMM) memory subsystem, when a particular data item is requested through the memory controller, a command packet is sent (via serial signaling) down a chain of buffer modules until the packet reaches a buffer chip that is connected to the Dynamic Random Access Memory (DRAM) chips that contains the requested data.

The buffer modules are often interconnected via a parallel Double Data Rate (DDR)-based interface. The buffer chip uses the DRAM protocol to access the data. The buffer is referred to as an AMB (advanced memory buffer). The AMB is designed to only take action in response to memory controller commands. The AMB delivers DRAM commands from the memory controller over the FBDIMM interface without any alteration to the DRAM devices over the parallel DDR-based interface.

DRAM chips are very high volume parts with many speed grades available at various costs. The time delay (i.e., the latency) at the memory controller to receive the data from the DRAM chips depends on the speed rating/grade of the parts. Also, another component of the time delay seen by the memory controller is the time taken for the command packet to reach the destination buffer chip and for that buffer chip to send the requested data once the buffer chip has obtained the data from the DRAM chips.

With FBDIMM technology, the signaling interface between the memory controller and the DRAM chips is split into two independent signaling interfaces, with a buffer between the two interfaces. The first interface between the buffer and DRAM chips supports DDR2 (DDR2 is the second (2) generation DDR interface standard, where DDR is a type of synchronous dynamic random access memory (SDRAM) memory access). However, the second interface between the memory controller and the buffer is a point-to-point serial interface.

Double-Data-Rate Synchronous Dynamic Random Access Memory (DDR SDRAM) achieves greater bandwidth than the preceding technology, single-data-rate (SDR) SDRAM, by transferring data on both the rising and falling edges of the clock signal. The greater bandwidth nearly doubles the transfer rate, without increasing the frequency of the front side bus. Thus a 100 MHz DDR system has an effective clock rate of 200 MHz when compared to equivalent SDR SDRAM. With data being transferred 8 bytes at a time, DDR RAM gives a transfer rate of (memory bus clock rate)×2 (for dual rate)×8 (number of bytes transferred). Thus with a bus frequency of 100 MHz, DDR-SDRAM gives a maximum transfer rate of 1600 Megabytes per second (MB/s) (i.e., DDR 1600 speeds).

Since the FBDIMM interface is based on serial differential signaling (similar to Serial Advanced Technology Attachment (ATA), Serial Small Computer System Interface (SCSI), Peripheral Computer Interconnect (PCI) Express, and others), a memory controller is capable of supporting multiple generations of FBDIMM technology-based components. FBDIMM technology, which is a new memory architecture, addresses the scaling needs of both capacity and bandwidth and enables memory to keep pace with processor and I/O improvements in enterprise platforms.

In an FBDIMM memory subsystem, there are two possible latency modes, fixed and variable. In the fixed latency mode, the buffer chips hold data when the buffer chips are near to the memory controller. The buffer chips also hold data when the DRAMs to which the buffer chips are attached are faster than the other buffer chips in the chain. The buffer chips hold data in order to make the total delay, as seen by the memory controller, the same for all data. The advantage of using a constant total delay is that the constant total delay greatly simplifies the design of the memory controller. However, the disadvantage is that all memory requests are delayed to match the delay of the slowest or farthest DRAM. Variable latency, in contrast, allows each buffer chip to return data as soon as possible. The benefit is, of course, that every data item is accessed in the minimum possible time. However, the drawback is that since all return data must pass through the same chain of buffer chips, a burden is placed on the memory controller to time the requests in a manner that avoids bus conflicts when returning data from different DRAMs.

SUMMARY OF THE INVENTION

Disclosed is a method and system for efficiently scheduling servicing of data requests in a Fully Buffered Dual Inline Memory Module (FBDIMM) memory sub-system, using the variable latency mode. High speed integrated circuitry embodies a scheduling algorithm which pre-computes return time parameters for Dynamic Random Access Memory (DRAM) data connected (via a parallel Double Data Rate (DDR)-based interface) to a plurality of buffer chips. The return time parameters are a compilation of all possible values for the time interval between sending a command packet from the memory controller to retrieve data from the various memory locations and receiving the requested data at the memory controller. Each possible value of the time interval is expressed as a binary vector, with one bit “on” (i.e., set to “1”). The algorithm stores the set of return time vectors in a table, for use by the memory controller when a memory access request is received.

For each data request received, the memory controller retrieves the appropriate return time vector by using an index associated with the memory address of the requested DRAM data (within a DRAM connected to a particular buffer). The scheduling algorithm also maintains a history vector representing a compilation (by logical OR operations) of return time vectors of all currently executing requests. The return time vector for each received request (i.e., requests that are awaiting execution) is compared (by logical AND operation) with the history vector to determine whether the received request presents a bus conflict to the already executing requests. In one embodiment, a bus conflict is identified by the presence of any “1” bits in the resulting vector following the AND operation.

The scheduling algorithm computes a score which indicates, relative to the other requests, how well the scheduling of each of the waiting requests at the next scheduling cycle preserves bandwidth, given the scheduled return of data, as indicated by the history vector. By utilizing the score for each request, the scheduling algorithm re-orders and issues requests in an order to preserve as much data bus bandwidth as possible, while avoiding bus conflicts. When a request is issued (executed) by the memory controller, the scheduling algorithm updates the history vector to reflect the inclusion of the newly issued request in the set of executing requests.

The above as well as additional objectives, features, and advantages of the present invention will become apparent in the following detailed written description.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention itself, as well as a preferred mode of use, further objects, and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 illustrates a block diagram of a data processing system within which features of the invention may be advantageously implemented;

FIG. 2 illustrates an FBDIMM memory subsystem;

FIG. 3 illustrates a block diagram representation of the circuitry which implements the scheduling algorithm;

FIG. 4 illustrates a table of vectors used for the determination of bus conflicts and the computation of vector sums and scores for a set of received data requests, according to an illustrative embodiment of the present invention;

FIG. 5 is a flow chart which illustrates the process completed by the algorithm for reordering data requests in a memory system operating in the variable latency mode, according to an illustrative embodiment of the present invention; and

FIG. 6 is a graph showing the results of a test of the scheduling algorithm, according to an illustrative embodiment of the present invention.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

The present invention provides a method and system for efficiently scheduling servicing of data requests in a Fully Buffered Dual Inline Memory Module (FBDIMM) memory sub-system, using the variable latency mode. High speed integrated circuitry embodies a scheduling algorithm which pre-computes return time parameters for Dynamic Random Access Memory (DRAM) data connected (via a parallel Double Data Rate (DDR)-based interface) to a plurality of buffer chips. The return time parameters are a compilation of all possible values for the time interval between sending a command packet from the memory controller to retrieve data from the various memory locations and receiving the requested data at the memory controller. Each possible value of the time interval is expressed as a binary vector, with one bit “on” (i.e., set to “1”). The algorithm stores the set of return time vectors in a table, for use by the memory controller when a memory access request is received.

For each data request received, the memory controller retrieves the appropriate return time vector by using an index associated with the memory address of the requested DRAM data (within a DRAM connected to a particular buffer). The scheduling algorithm also maintains a history vector representing a compilation (by logical OR operations) of return time vectors of all currently executing requests. The return time vector for each received request (i.e., requests that are awaiting execution) is compared (by logical AND operation) with the history vector to determine whether the received request presents a bus conflict to the already executing requests. In one embodiment, a bus conflict is identified by the presence of any “1” bits in the resulting vector following the AND operation.

The scheduling algorithm computes a score which indicates, relative to the other requests, how well the scheduling of each of the waiting requests at the next scheduling cycle preserves bandwidth, given the scheduled return of data, as indicated by the history vector. By utilizing the score for each request, the scheduling algorithm re-orders and issues requests in an order to preserve as much data bus bandwidth as possible, while avoiding bus conflicts. When a request is issued (executed) by the memory controller, the scheduling algorithm updates the history vector to reflect the inclusion of the newly issued request in the set of executing requests.

In the following detailed description of exemplary embodiments of the invention, specific exemplary embodiments in which the invention may be practiced are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, architectural, programmatic, mechanical, electrical and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.

Within the descriptions of the figures, similar elements are provided similar names and reference numerals as those of the previous figure(s). Where a later figure utilizes the element in a different context or with different functionality, the element is provided a different leading numeral representative of the figure number (e.g, 1 xx for FIGS. 1 and 2 xx for FIG. 2). The specific numerals assigned to the elements are provided solely to aid in the description and not meant to imply any limitations (structural or functional) on the invention.

It is also understood that the use of specific parameter names are for example only and not meant to imply any limitations on the invention. The invention may thus be implemented with different nomenclature/terminology utilized to describe the above parameters, without limitation.

With reference now to the figures, FIG. 1 depicts a block diagram representation of a basic data processing system within which features of the invention may be advantageously implemented. DPS 100 comprises processor 101 connected to system bus/interconnect 102 and memory 106. Controlling access to memory 106 is memory controller 105, which is also connected to system bus/interconnect 102. Memory controller 105 comprises hardware and software logic that enables memory controller 105 to control access to (i.e., retrieval and storage of) memory data stored within memory 106.

Those of ordinary skill in the art will appreciate that the hardware and basic configuration depicted in FIG. 1 may vary. The depicted example is not meant to imply architectural limitations with respect to the present invention. The data processing system depicted in FIG. 1 may be, for example, an IBM eServer pSeries system, a product of International Business Machines Corporation in Armonk, N.Y., running the Advanced Interactive Executive (AIX) operating system or LINUX operating system.

Various features of the invention are provided as firmware code and/or logic within memory controller 105. Among the firmware code are code for providing serial signaling functionality between memory controller 105 and memory components, code for enabling the DRAM protocol connection to access memory data, and more specific to the invention, code for enabling the variable latency scheduling features described below. For simplicity, the collective body of code and logic that enables the variable latency scheduling features is referred to herein as variable latency scheduling utility. In actual implementation, the variable latency scheduling utility may be implemented in a memory subsystem operating in a variable latency mode to provide the variable latency scheduling functionality described below.

Thus, as shown by FIG. 1, in addition to the above described hardware components, memory controller 105 of data processing system 100 comprises one or more firmware components, including variable latency scheduling (VLS) utility 110. According to the illustrative embodiment, variable latency scheduling utility 110 enables memory controller 105 to complete a series of functional processes, including: (1) pre-computing latency associated with the retrieval of memory data, connected to all possible buffer chips; (2) maintaining a history vector which provides information about the scheduled return of data associated with currently executing requests; (3) retrieving a return time vector for a received data request from the (pre-computed) return time parameters; (4) determining which received request to schedule as a next executing request at the next scheduling cycle; and other features/functionality described below and illustrated by FIGS. 2-6.

FIG. 2 illustrates an FBDIMM memory subsystem. Memory subsystem 200 comprises memory controller 105 connected to a chain of buffers illustrated as buffer set 202, via serial link 201. Memory subsystem 200 also comprises a number of Dynamic Random Access Memory banks 203, which are assumed to be FBDIMMs. The buffers within buffer set 202 are connected to the DRAM chips within the respective DRAM banks via a parallel Double Data Rate (DDR)-based interface, which is illustrated as DDR2 interface 204.

The FBDIMM technology directs signaling interface between memory controller 105 and the DRAM chips 203, and the interface is split into two independent signaling interfaces with a buffer, referred to as the AMB (advanced memory buffer), between the two interfaces. The parallel interface between the buffer and DRAM chips supports DDR2. However, the interface between the memory controller and the buffer is a point-to-point serial interface.

Memory subsystem 200 consists of several circuits which are carefully designed to embody a scheduling algorithm (within VLS utility 110 in memory controller 105 of FIG. 1) in a manner that is practical to implement in a very high speed integrated circuit chip. In optimizing the design of the scheduling algorithm, the performance benefits are maximized when special consideration is given to the following factors: (1) The number of logic gates; and (2) the length of interconnecting wires. These two (2) factors, which may vary according to the embedded technology, may also decrease the speed at which a circuit operates. Fortunately, the scheduling algorithm operates ideally (having factored the number of logic gates and the length of connecting wire into the design) in FBDIMM technology, when operating in variable latency mode at DDR1600 speeds. It is contemplated that a higher performance solution at a particular speed and in a particular circuit technology may be ideally achieved by a certain level of redesign (which also factors the number of logic gates and length of connecting wire).

Memory subsystem 200 operates in the variable latency mode, which allows each buffer chip within buffer set 202 to return data in the minimum time possible. In order to avoid data bus conflicts and to execute requests as quickly and as efficiently as possible, a scheduling algorithm (which is illustrated in FIG. 3) implemented as VLS utility 110 within memory controller 105 (FIG. 1) is provided. During memory access operation, the scheduling algorithm pre-computes the latency information (i.e., the return time information) associated with all data requests and utilizes this latency information to determine the latency associated with each subsequent request for memory data. The number of buffer chips in buffer set 202 (i.e., a chain of buffers) indicates the number of the different latency values that are possible. Thus, a buffer set with eight buffers in the chain, for example, indicates that there are eight possible latency values.

The return time information (latency) for data connected to each buffer chip is expressed as a return time (binary) vector with only one bit turned on (equivalent to a binary “1” and referred to as a “1” bit). Therefore, a binary vector of eight single bit components, with only one “1” bit, may account for all of the eight possible values of the latency. Data requests with the smallest associated latency (e.g., requests targeting memory data in the buffer chip(s) that are closest to memory controller 105) have an associated return time vector in which the leftmost bit (the first component) of the vector is the “1” bit. Data requests with a maximum associated latency (i.e., requests targeting memory data in the buffer chip(s) that are farthest away from memory controller 105) have an associated return time vector in which the rightmost bit (e.g., the eighth component, given the eight buffer example) of the vector is the “1” bit.

The scheduling algorithm uses these return time vectors to compile a history vector of requests selected for execution. The scheduling algorithm then uses this history vector to further determine the potential conflicts presented by subsequently received requests to the currently executing requests. In addition, the scheduling algorithm executes a “sums” and “scores” computation process (which are illustrated in FIG. 4) to select a “waiting” request to begin executing at the next cycle at which selected requests may be scheduled.

FIG. 3 illustrates a block diagram representation of the circuitry (or scheduling logic) that implements various functions of the scheduling algorithm. Scheduling logic 300 comprises a set of sequentially-ordered data return time vectors 302, which are looked-up/retrieved from a list of pre-computed values based on which DRAM contains the data for new requests 301 received at the memory controller 105 (FIG. 1). Scheduling logic 300 also comprises conflict indicator vector 311 and scores vector 312, which are connected to and provide control input for request selector 310. Both conflict indicator vector 311 and scores vector 312 contain parameter values corresponding to respective entries of the set of data return time vectors 302. Specific functionality of conflict indicator vector 311 and scores vector 312 is explained in greater detail below.

Request selector 310 provides a select input to multiplexor (MUX) 309, which is connected to data return time vectors 302. Also connected to data return time vectors 302 is a set of adders 303, which are utilized for providing the sums of the columns of entries for the return time vectors. Determination and use of resulting sums is described in further detail below within the description of the table of FIG. 4.

Scheduling logic 300 also comprises a series of AND logic (not shown) that are utilized to logically AND each return time vector with the current history vector. According to one embodiment the results of the ANDing process are stored within respective entries of conflicts vector 311. The purpose for completing the logically ANDing of these data return time vectors with the history vector and deductions discerned from the resulting sum vector are explained with reference to FIG. 4, described below.

Within scheduling logic 200, MUX 309 receives vector entries as inputs via input lines, MUXin lines 304, coupled to data return time vectors 302, and MUX 309 provides selected vector entries as outputs via output lines, MUXout lines 305, which are each coupled to a first input of a set of logical OR gates 308. The second input of the set of OR gates 308 are connected to outputs of a series of latches 307. These latches contain the accumulation of the previous selections, which is referred to as the history vector (306).

Scheduling logic 300 further includes a history vector 306 which is a set of bits of equal number to the size of the data return time vectors 302. The history vector 306 is the latched output from the above ORing process with the leftmost bit shifted out of the vector and the rightmost bit set to zero via grounding. This vector (306) is determined by first selecting a particular data return time vector (from vectors 302) corresponding to a particular received request that is selected at MUX 309 by request selector 310. Once the particular data return time vector is selected, the vector entries are inputted to a set of OR gates 308 and are ORed with a previous set of entries of the current history vector, which are stored within the series of latches 307. The ORing of the selected data return time vector with the current history vector then generates the new history vector 306.

With scheduling logic 300, new requests 301 are received at memory controller 105. The return time vectors associated with the new requests 301 are placed in data return time vectors 302. Conflicts presented by the received requests to the executing requests are identified within conflict indicator vector 311. Adders (303) are utilized in the computation of the sums. The sums vector, the conflict vector 311, and the scores vector 312 are utilized to determine the “waiting” request that is the next scheduled request to begin executing. The history vector provides compiled return time information for data being requested by all of the currently executing requests.

Data may be returned in a multiple of “n” clock cycles, where n refers to the minimum number of clock cycles between successive returns of data at the memory controller. In the diagram and discussion, the value “n” is also proportional to the shortest interval between sending a command packet from the memory controller and receiving the associated data at the memory controller. This interval corresponds to the short delay associated with retrieving data connected to the buffer chips that are closest to the memory controller or retrieving data from the faster DRAMs. Depending on the time delays involved in the actual implementation, this first delay may be larger than the number of clock cycles between successive transfers. Since this delay is added to all accesses, the delay does not alter the algorithm. Request selector 310 triggers MUX 309 to forward (via the MUXout lines 305) the return time vector of the selected request to the respective first inputs of the OR gates 308. The history vector 306 (provided by the outputs of the latch set 307) further provides the other set of (second) inputs to the respective OR gates 300. In scheduling logic 300, the OR gates provide the logical OR operations for incorporating the return time vector for the selected request into the history vector 306. At the next scheduling clock cycle, the history vector 306 is updated with data from the MUXout lines 305 via the OR gates 308. During the updating of the history vector 306, the expired vector component (i.e., the leftmost bit) is removed from the history vector 306.

Turning now to FIG. 4, a table of vectors used for the determination of conflict and the computation of “sums” and “scores” for a set of received data requests is illustrated, according to an illustrative embodiment of the present invention. Table 400 comprises history vector 401 which is located in the first row of Table 400. In addition, Table 400 includes data return time vectors 403. Data return time vectors 403 correspond to the respective requests received at memory controller 105. Data return time vectors 403 are included in Table 400 (below the row containing history vector 401) in the order that the respective requests were received. Additionally, Table 400 includes conflict vector column 407, which has specific ones of the entries set to “1”, indicating a conflict for first return time vector, third return time vector, and sixth return time vector. Table 400 also comprises sum vector 405, which is a row of sums corresponding to the various requests. Finally, Table 400 also comprises a scores vector column 409, illustrated as a separate, independent vector, which is the “last” or “rightmost” column depicted.

The scheduling algorithm determines the potential conflict presented by each received request if the received request begins executing following the next scheduling cycle. In Table 400, the components of return time vectors 403 that have a “1” bit in the same column as history vector 401, correspond to the respective received requests which present a conflict to the currently executing requests. The scheduling algorithm determines the conflict presented by a single request by performing a logical AND operation on history vector 401 and the return time vector (corresponding to the single request). The logical AND operation is repeated for each of the received requests. The corresponding resulting vector (from performing the logical AND operation) indicates a conflict if any “1” bits are present in the resulting vector. If there is conflict (as indicated by the presence of a “1” bit in the resulting vector), a corresponding conflict indicator in conflict vector column 407 (or conflict vector 311, FIG. 3) is set to “1”.

In Table 400, conflict indicators for first return time vector, third return time vector and the sixth return time vector all demonstrate the presence of conflict with “1” bits placed in the appropriate position of conflict vector column 407. Thus, the first received request, the third received request and the sixth received request each present a conflict to the currently executing requests and, thus, none of these three requests are selected to begin executing at the next scheduling cycle.

The sums within sum vector 405 are computed as follows. The computation of the column sum for the first column starts with “0”. For all columns besides the first column, the computation of a particular column sum starts with the column sum from the previous column. The previous column sum (or “0” for the first column) is then added to the number of “1” bits in the column for which the column sum is being computed. Then “1” is subtracted after adding the number of “1” bits as long as the value (after the addition of “1 bits) is not equal to “0”. The sums are contained in sum vector 405. The sums give an indication of the clustering of requested time slots (including the already scheduled time slots) for data return.

By construction, the return time vector associated with each request has exactly one bit on, and the score for each request, which is stored in scores column 409, is (identified as) the column sum preceding the column in which the (return time) vector's only “1” bit is present. Requests with a “1” bit in the leftmost column have a score of “0” as long as these requests do not have a conflict. For example, the second received request has a score of “0” and is the request with the lowest score, and which does not present a conflict. Thus, in the example illustrated in Table 400, request 2 is the received request that is selected to begin executing at/during the next scheduling cycle. A particular request selection, using the scores criteria, is made to best reduce the clustering of requested time slots (i.e., to evenly distribute the servicing of the requests) to service requests more efficiently, while avoiding conflict.

The history vector and the collection of return time vectors (associated with the received requests) are all updated at each scheduling cycle. In particular, the scheduling algorithm begins to update history vector 401 by first incorporating the return time vector of the selected request (into history vector 401). The update is executed by a logical ORing of history vector 401 and the return time vector. The scheduling algorithm then removes the expired (first) vector component (bit) of history vector 401, at the scheduling cycle. This bit removal corresponds to a left (time) shift of history vector 401 in Table 400. Also, the set of data return time vectors below the selected return time vector is shifted upwards in Table 400, after removing the selected request and associated data return time vector from the set within Table 400. This upward shifting is provided to maintain the receiving order and to accept, in the order that requests are received, any new requests.

FIG. 5 is a flow chart which illustrates the processes completed by the algorithm for reordering data requests and for avoiding conflicts in a memory subsystem operating in the variable latency mode, according to an illustrative embodiment of the present invention. The process begins at block 501, at which, high speed integrated circuitry embodying the scheduling algorithm pre-computes the return time data for data connected to all possible DRAM buffer chips. The return time information for data connected to each buffer chip is expressed as a binary vector with only one bit turned on (equivalent to a binary “1” and referred to as a “1” bit). When data may be returned in the minimum amount of time, the leftmost bit of the vector is the “1” bit and when the data is capable of making a return in the maximum amount of time, the rightmost bit of the vector is the “1” bit. The compiled set of binary return time vectors for data connected to all buffer chips may be referred to as a set/collection of return time vectors which are stored in a table that is accessed following receipt of each memory access request by the memory controller. At block 502, the scheduling algorithm maintains the history vector, which indicates the expected arrival time of data returning to the memory controller. In particular, the history vector is maintained in a chain of latches and is also expressed as a binary vector. If no memory requests are being executed, or if all prior requests have been completed, the history vector is a vector of zeros.

Any new request presented to the memory controller is associated with a data return time vector (retrieved from the pre-computed return time information), as shown in block 503. The memory controller maintains a list of multiple memory requests which have been issued to the memory controller by a microprocessor or other consumer of data. Each request has an associated data return time vector. These return time vectors are each intentionally expressed as a binary vector with only one bit turned on to align the return time vectors with the history vector by time scale. This alignment of time scales allows the history vector to be logically ANDed with the return time vector for a particular access request to determine if that request causes a conflict with the requests that have already been issued.

In order to begin the process for determining if a new request presents any scheduling conflict to the executing requests, circuitry embodying the algorithm performs a logical ANDing operation between each data return time vector (for each new request) and the history vector, as shown at block 504. At block 505, the resulting vector is inspected to determine if a zero vector was produced. At block 507, the algorithm determines whether there is a conflict (i.e., whether the logical ANDing operation resulted in a nonzero vector). If a conflict exists, then the algorithm confirms that the new request does present a conflict to the executing requests and places a “1” in the appropriate space of the conflict vector, as shown at block 508. If, at block 507, the algorithm determines that the result of the logical ANDing operation does not indicate existence of a conflict (i.e., the logical ANDing operation resulted in a zero vector), then a “0” is placed in the appropriate space of the conflict vector to indicate that the new request does not present a conflict to the executing requests, as shown at block 509.

At block 510, at which, the algorithm computes the sums for each column and, at block 511, the algorithm determines the score for each request. The algorithm then selects the requests having the lowest score (or the first received request among multiple requests having the same lowest score) that does not have a conflict, as shown at block 512. A tabular illustration of rows and columns for the computation of sums and scores is depicted in FIG. 4.

The sums and scores computation is used to efficiently service a higher number of requests in a shorter space of time by re-ordering the requests while “preserving” as much bandwidth as possible. Preserving bandwidth refers to the efficient use of available bandwidth, i.e., with minimal waste of bandwidth, while avoiding data bus conflicts. In order to attain the theoretical maximum limit of bandwidth usage, data returns every n cycles, i.e., data occupies every possible time slot on the bus. The re-ordering process (or requests) maximizes the ability to take advantage of every available opportunity or available time-slot for transmitting data between the memory controller and the buffer chips.

In order to account for the start of execution and to track the return time of the selected request, the algorithm performs a logical ORing operation between the data return time vector corresponding to the selected request and the history vector, at block 513. As shown at block 514, the history vector is updated at the scheduling cycle, in time for the next sums and scores computation. Additionally, as shown at block 515, all the data return time vectors below the selected request vector are shifted one table row upwards, after the selected vector is removed from the table. Shifting of the vectors within the table is necessary to update the vectors at the scheduling cycles. Any new vector/new request is be added to the end of the table/matrix of vectors/requests, as shown at block 516, and the process ends at block 517.

FIG. 6 illustrates a graph showing the results of a C language program which was coded to test the scheduling algorithm, according to an illustrative embodiment of the present invention. Graph 600 comprises throughput axis 601, and configuration axis 602. Graph 600 depicts the throughput measured as a percentage of total possible bus bandwidth for both an in order request ordering versus the ordering produced by the scheduling algorithm for 1000 different memory configurations. Each experiment is run through 1000 random requests and the total throughput is measured. Each memory configuration consists of different speed grade DRAMs plugged into the FBDIMM channel in different orders. Across all of the experiments, an average gain in bus throughput is observed, and the new algorithm improves throughput in substantially all of the experiments.

In the flow chart (FIG. 5) above, while the process steps are described and illustrated in a particular sequence, use of a specific sequence of steps is not meant to imply any limitations on the invention. Changes may be made with regards to the sequence of steps without departing from the spirit or scope of the present invention. Use of a particular sequence is therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.

As a final matter, it is important that while an illustrative embodiment of the present invention has been, and will continue to be, described in the context of a fully functional computer system with installed software, those skilled in the art will appreciate that the software aspects of an illustrative embodiment of the present invention are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the present invention applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of signal bearing media include recordable type media such as floppy disks, hard disk drives, CD ROMs, and transmission type media such as digital and analogue communication links.

While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. 

1. In a memory subsystem having a plurality of buffer chips with different access latencies associated with retrieving memory data from memory components associated with the buffer chips, a memory controller comprising: logic for retrieving a return time vector for a received data request from a table of return time information; and logic for deterministically selecting a next request to schedule to begin executing at a next scheduling cycle based on a data return time vector for that next request compared with a history vector of currently executing requests, wherein said next request is a request that does not provide a data bus conflict with the currently executing requests and which results in maximum usage of data bus bandwidth between the buffer chips and the memory controller.
 2. The memory controller of claim 1, further comprising: logic for providing a next history vector by ORing the return time vector for the next request selected for execution at the next scheduling cycle with a previously-generated history vector of all currently executing requests; logic for position-shifting the previously-generated history vector to generate the next history vector by (a) removing an entry within the previously-generated history vector corresponding to a request that has completed its execution and returned its data to the memory controller and (b) adding a new entry for the next request.
 3. The memory controller of claim 1, wherein said logic for deterministically selecting further comprises: logic for pre-computing a table of return time information for memory data stored within a memory component of respective ones of the plurality of buffer chips; logic for calculating the data return time information in a unit of time; logic for expressing the data return time information as a plurality of binary return time vectors with a single bit turned on having a bit value of “1”; and logic for storing the first plurality of data return time vectors in the table.
 4. The memory controller of claim 2, wherein said logic for providing further comprises: logic for initializing the history vector with a vector of zeros; and logic for updating the history vector when the received request becomes the next executing request.
 5. The memory controller of claim 1, wherein said logic for deterministically selecting further comprises: logic for determining when a received request presents a conflict to the currently executing requests; logic for computing a vector of sums from the return time vectors; and logic for computing a score for each one of the data return time vectors provided for a respective received request.
 6. The memory controller of claim 5, further comprising: logic for identifying a single received request with a lowest score and whose execution presents no data bus conflict; when the single received request has the lowest score, logic for selecting said single received request to schedule as the next executing request; and when more than one received request has the (same) lowest score, logic for selecting the older of the received requests to schedule as the next executing request.
 7. The memory controller of claim 2, further comprising: logic for performing a logical OR operation with the history vector and with the data return time vector of the next executing request, wherein said logical OR operation incorporates said return time vector into said history vector; and logic for removing an expired element from the history vector.
 8. In a memory controller that receives data requests and initiates data accesses to memory components accessible via a plurality of buffer chips with different access latencies, a method comprising: retrieving a data return time vector for a received data request from a table of return time information; and deterministically selecting a next request to schedule to begin executing at a next scheduling cycle based on a data return time vector for that next request compared with a history vector of currently executing requests, wherein said next request is a request that does not provide a data bus conflict with the currently executing requests and which results in maximum usage of data bas bandwidth between the buffer chips and the memory controller.
 9. The method of claim 8, further comprising: providing a next history vector by ORing the return time vector for the next request selected for execution at the next scheduling cycle with a previously-generated history vector of all currently executing requests; position-shifting the previously-generated history vector to generate the next history vector by (a) removing an entry within the previously-generated history vector corresponding to a request that has completed its execution and returned its data to the memory controller and (b) adding a new entry for the next request.
 10. The method of claim 8, wherein deterministically selecting further comprises: pre-computing a table of return time information for memory data stored within a memory component of respective ones of the plurality of buffer chips; calculating the return time information in a unit of time; expressing the return time information as a plurality of binary return time vectors with a single bit turned on having a bit value of “1”; storing the first plurality of data return time vectors in the table. initializing the history vector with a vector of zeros; and updating the history vector when the received request becomes the next executing request.
 11. The method of claim 9, wherein said deterministically selecting further comprises: determining when a received request presents a conflict to the currently executing requests; computing a vector of sums from the return time vectors; and computing a score for each one of the return time vectors provided for a respective received request.
 12. The method of claim 11, further comprising: identifying a single received request with a lowest score and whose execution presents no data bus conflict; when the single received request has the lowest score, selecting said single received request to schedule as the next executing request; and when more than one received request has the (same) lowest score, selecting the older of the received requests to schedule as the next executing request.
 13. The method of claim 9, further comprising: performing a logical OR operation with the history vector and with the data return time vector of the next executing request, wherein said logical OR operation incorporates said data return time vector into said history vector; and removing an expired element from the history vector.
 14. A data processing system comprising: a processing component that generates data requests and issues the data requests for a return of data; a memory subsystem coupled to the processing component, said memory subsystem having a plurality of buffer chips with different access latencies associated with retrieving memory data from memory components associated with the buffer chips; and a memory controller associated with the memory subsystem, said memory controller having: logic for pre-computing a table of return time information for memory data stored within a memory component of respective ones of the plurality of buffer chips; logic for calculating the return time information in a unit of time; logic for expressing the return time information as a plurality of binary return time vectors with a single bit turned on having a bit value of “1”; and logic for storing the first plurality of data return time vectors in a table of return time information; logic for retrieving a data return time vector for a received data request from the table of return time information; and logic for deterministically selecting a next request to schedule to begin executing at a next scheduling cycle based on a data return time vector for that next request compared with a history vector of currently executing requests, wherein said next request is a request that does not provide a data bus conflict with the currently executing requests and which results in maximum usage of data has bandwidth between the buffer chips and the memory controller.
 15. The data processing system of claim 14, wherein the memory controller, further comprises: logic for providing a next history vector by ORing the data return time vector for the next request selected for execution at the next scheduling cycle with a previously-generated history vector of all currently executing requests; logic for position-shifting the previously-generated history vector to generate the next history vector by (a) removing an entry within the previously-generated history vector corresponding to a request that has completed its execution and returned its data to the memory controller and (b) adding a new entry for the next request.
 16. The data processing system of claim 15, wherein said logic for providing further comprises: logic for initializing the history vector with a vector of zeros; and logic for updating the history vector when the received request becomes the next executing request.
 17. The data processing system of claim 14, wherein said logic for deterministically selecting further comprises: logic for determining when a received request presents a conflict to the currently executing requests; logic for computing a vector of sums from the data return time vectors; and logic for computing a score for each one of the data return time vectors provided for a respective received request.
 18. The data processing system of claim 14, wherein the memory controller further comprises: logic for identifying a single received request with a lowest score and whose execution presents no data bus conflict; when the single received request has the lowest score, logic for selecting said single received request to schedule as the next executing request; and when more than one received request has the (same) lowest score, logic for selecting the older of the received requests to schedule as the next executing request.
 19. The data processing system of claim 14, wherein the memory controller further comprises: logic for performing a logical OR operation with the history vector and with the data return time vector of the next executing request, wherein said logical OR operation incorporates said data return time vector into said history vector; and logic for removing an expired element from the history vector.
 20. The data processing system of claim 14, wherein the memory subsystem operates in a variable latency mode. 